snapcraft enable-ci travis asks you to confirm y/N after a wall of text. However, there's no question in that text. You do not know what you're confirming. So, I think: 1) Snapcraft should say, "do you wish to continue". 2) It should default to yes. We have no reason to not be confident in this operation 3) We should drop the "EXPERIMENTAL" line. This feature has been present for ages. $ snapcraft enable-ci travis Snapcraft integration for Travis (CI). This is an *EXPERIMENTAL* feature and subject to incompatible changes in the future, please use with caution. This command currently depends on a working `travis` CLI environment and a previously initialized Travis project (`.travis.yml`). Make sure your Travis project is also configured to "Build pushes", this way every new push to `master` will result in a new snap revision in the Store. This operation will acquire properly attenuated Store credentials and encrypt them for use in your testbed (`.snapcraft/travis_snapcraft.cfg`), only Travis has the private key to decrypt it and will be only available to branches of the same repository, not forks. Then it will adjust Travis configuration ('.travis.yml') with the commands to decrypt credentials during 'after_success' phase and install latest `snapcraft` to build and release your snap (inside a snapcore/snapcraft docker container) during the 'deploy' phase. See the example below:: sudo: required services: - docker after_success: - openssl aes-256-cbc -K <travis-key> -iv <travis-iv> -in .snapcraft/travis_snapcraft.cfg -out .snapcraft/snapcraft.cfg -d deploy: skip_cleanup: true provider: script script: docker run -v $(pwd):$(pwd) -t snapcore/snapcraft sh -c "apt update -qq && cd $(pwd) && snapcraft && snapcraft push *.snap --release edge" on: branch: master The dedicated credentials will be functional for exactly 1 year or until a password change on the related Ubuntu One SSO account. In order to refresh the project credentials, please run the following command:: $ snapcraft enable-ci travis --refresh [y/N]: y